Systems and methods for error correction

ABSTRACT

A method for error correction and a system. The method may include opening a selected row of a memory bank out of multiple memory banks of a dynamic memory module; and while the selected row is open: (i) receiving selected data sub-blocks that are targeted to be written to the selected row, (ii) calculating selected error correction code sub-blocks that are related to the selected data sub-blocks, (iii) caching the selected error correction code sub-blocks in a cache memory that differs from the dynamic memory module and (iv) writing, to the selected row, the selected error correction code sub-blocks.

CROSS REFERENCE

This application claims priority of U.S. provisional patent Ser. No.62/486,006, filing date Apr. 17, 2017 which is incorporated herein inits entirety.

BACKGROUND

Advanced driver assistance systems (ADAS), and autonomous vehicle (AV)systems use cameras and other sensors together with object classifiers,which are designed to detect specific objects in an environment of avehicle navigating a road. Object classifiers are designed to detectpredefined objects and are used within ADAS and AV systems to controlthe vehicle or alert a driver based on the type of object that isdetected its location, etc.

As ADAS and AV systems progress towards fully autonomous operation, itwould be beneficial to protect data generated by these systems.

SUMMARY

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar parts.While several illustrative embodiments are described herein,modifications, adaptations and other implementations are possible. Forexample, substitutions, additions, or modifications may be made to thecomponents illustrated in the drawings, and the illustrative methodsdescribed herein may be modified by substituting, reordering, removing,or adding steps to the disclosed methods. Accordingly, the followingdetailed description may be not limited to the disclosed embodiments andexamples.

Disclosed embodiments provide systems and methods that can be used aspart of or in combination with autonomous navigation/driving and/ordriver assist technology features. Driver assist technology refers toany suitable technology to assist drivers in the navigation and/orcontrol of their vehicles, such as FCW, LDW and TSR, as opposed to fullyautonomous driving.

There may be provided a method for error correction, the method mayinclude opening a selected row of a memory bank out of multiple memorybanks of a dynamic memory module; receiving selected data sub-blocks,while the selected row may be open, by the dynamic memory module,wherein the selected data sub-blocks are received over a communicationlink and are targeted to be written to the selected row; calculating,while the selected row may be open and by an error correction unit,selected error correction code sub-blocks that are related to theselected data sub-blocks; caching the selected error correction codesub-blocks in a cache memory that differs from the dynamic memorymodule; writing, to the selected row, the selected error correction codesub-blocks while the selected row may be open; wherein the writing mayinclude sending the selected error correction code sub-blocks to thedynamic memory module over the communication link; and closing theselected row.

There may be provided a system having error correction capabilities, thesystem may include a dynamic memory controller, a dynamic memory modulethat may be coupled to a communication link; a cache memory, and anerror correction code unit; wherein the dynamic memory controller may bearranged to (a) open a selected row of a memory bank out of multiplememory banks of a dynamic memory module; (b) receive, while the selectedrow may be open, selected data sub-blocks that are targeted to bewritten to the selected row; wherein the dynamic memory module may beconfigured to receive the selected data sub-blocks from the dynamicmemory controller and over a communication link; wherein the errorcorrection unit may be arranged to calculate, while the selected row maybe open, selected error correction code sub-blocks that are related tothe selected data sub-blocks; wherein the cache memory differs from thedynamic memory module and may be arranged to cache the selected errorcorrection code sub-blocks; wherein the dynamic memory controller may bealso arranged to (a) send the selected error correction code sub-blocksto the dynamic memory module over the communication link; (b) write, tothe selected row and over the communication link, the selected errorcorrection code sub-blocks while the selected row may be open; and (c)close the selected row.

There may be provided a computer program product that storesinstructions that once executed by a computerized system may cause thecomputerized system to execute the steps of: opening a selected row of amemory bank out of multiple memory banks of a dynamic memory module;receiving selected data sub-blocks, while the selected row may be open,by the dynamic memory module; wherein the selected data sub-blocks arereceived over a communication link and are targeted to be written to theselected row; calculating, while the selected row may be open and by anerror correction unit, selected error correction code sub-blocks thatare related to the selected data sub-blocks; caching the selected errorcorrection code sub-blocks in a cache memory that differs from thedynamic memory module; writing, to the selected row, the selected errorcorrection code sub-blocks while the selected row may be open; whereinthe writing may include sending the selected error correction codesub-blocks to the dynamic memory module over the communication link; andclosing the selected row.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this disclosure, illustrate various disclosed embodiments. Inthe drawings:

FIG. 1 is a block diagram representation of a system consistent with thedisclosed embodiments;

FIG. 2A is a diagrammatic side view representation of an exemplaryvehicle including a system consistent with the disclosed embodiments;

FIG. 2B is a diagrammatic top view representation of the vehicle andsystem shown in FIG. 2A consistent with the disclosed embodiments;

FIG. 2C is a diagrammatic top view representation of another embodimentof a vehicle including a system consistent with the disclosedembodiments;

FIG. 2D is a diagrammatic top view representation of yet anotherembodiment of a vehicle including a system consistent with the disclosedembodiments;

FIG. 2E is a diagrammatic representation of exemplary vehicle controlsystems consistent with the disclosed embodiments;

FIG. 3 is a diagrammatic representation of an interior of a vehicleincluding a rearview mirror and a user interface for a vehicle imagingsystem consistent with the disclosed embodiments;

FIG. 4 is a block diagram of a dynamic memory module, a dynamic memorycontroller, an error correction code unit consistent with the disclosedembodiments;

FIG. 5 is a block diagram of a dynamic memory module and a dynamicmemory controller that includes an error correction code unit consistentwith the disclosed embodiments;

FIG. 6 illustrates timing diagrams consistent with the disclosedembodiments;

FIG. 7 illustrates a method consistent with the disclosed embodiments;and

FIG. 8 illustrates a method consistent with the disclosed embodiments.

DETAILED DESCRIPTION

Before discussing in detail examples of features of the error correctioncoding and memory management of a dynamic memory module of a system thatmay provide a variety of features related to autonomous driving,semi-autonomous driving and/or driver assist technology.

The system may be arranged to process images of an environment ahead ofa vehicle navigating a road for training a neural networks or deeplearning algorithms to estimate a future path of a vehicle based onimages or feature of the processing of images of an environment ahead ofa vehicle navigating a road using a trained neural network to estimate afuture path of the vehicle.

There may be provided various possible implementations andconfigurations of a vehicle mountable system that can be used forcarrying out and implementing the methods according to examples of thepresently disclosed subject matter. In some embodiments, variousexamples of the system can be mounted in a vehicle and can be operatedwhile the vehicle is in motion. In some embodiments, the system canimplement the methods according to examples of the presently disclosedsubject matter.

However, it would be appreciated that embodiments of the presentdisclosure are not limited to scenarios where a suspected upright objectindication is caused by a high-grade road. The suspected upright objectindication can be associated with various other circumstances and canresult from other types of image data and also from data that is notimage based or is not exclusively image based, as well.

FIG. 1, to which reference is now made, is a block diagramrepresentation of a system consistent with the disclosed embodiments.System 100 can include various components depending on the requirementsof a particular implementation. In some examples, system 100 can includea processing unit 110, an image acquisition unit 120 and one or morememory units 140, 150. Processing unit 110 can include one or moreprocessing devices. In some embodiments, processing unit 110 can includean application processor 180, an image processor 190, or any othersuitable processing device. Similarly, image acquisition unit 120 caninclude any number of image acquisition devices and components dependingon the requirements of a particular application. In some embodiments,image acquisition unit 120 can include one or more image capture devices(e.g., cameras), such as image capture device 122, image capture device124, and image capture device 126. In some embodiments, system 100 canalso include a data interface 128 communicatively connecting processingunit 110 to image acquisition device 120. For example, data interface128 can include any wired and/or wireless link or links for transmittingimage data acquired by image acquisition device 120 to processing unit110.

Both application processor 180 and image processor 190 can includevarious types of processing devices. For example, either or both ofapplication processor 180 and image processor 190 can include one ormore microprocessors, preprocessors (such as image preprocessors),graphics processors, central processing units (CPUs), support circuits,digital signal processors, integrated circuits, memory, or any othertypes of devices suitable for running applications and for imageprocessing and analysis. In some embodiments, application processor 180and/or image processor 190 can include any type of single or multi-coreprocessor, mobile device microcontroller, central processing unit, etc.Various processing devices can be used, including, for example,processors available from manufacturers such as Intel®, AMD®, etc. andcan include various architectures (e.g., x86 processor, ARM®, etc.).

In some embodiments, application processor 180 and/or image processor190 can include any of the EyeQ series of processor chips available fromMobileye®. These processor designs each include multiple processingunits with local memory and instruction sets. Such processors mayinclude video inputs for receiving image data from multiple imagesensors and may also include video out capabilities. In one example, theEyeQ2® uses 90 nm-micron technology operating at 332 Mhz. The EyeQ2®architecture has two floating point, hyper-thread 32-bit RISC CPUs(MIPS32@ 34K® cores), five Vision Computing Engines (VCE), three VectorMicrocode Processors (VMP®), Denali 64-bit Mobile DDR Controller,128-bit internal Sonics Interconnect, dual 16-bit Video input and 18-bitVideo output controllers, 16 channels DMA and several peripherals. TheMIPS34K CPU manages the five VCEs, three VMP™ and the DMA, the secondMIPS34K CPU and the multi-channel DMA as well as the other peripherals.The five VCEs, three VMP® and the MIPS34K CPU can perform intensivevision computations required by multi-function bundle applications. Inanother example, the EyeQ3®, which is a third-generation processor andis six times more powerful that the EyeQ2®, may be used in the disclosedexamples. In yet another example, the EyeQ4®, the fourth-generationprocessor, may be used in the disclosed examples.

While FIG. 1 depicts two separate processing devices included inprocessing unit 110, more or fewer processing devices can be used. Forexample, in some examples, a single processing device may be used toaccomplish the tasks of application processor 180 and image processor190. In other embodiments, these tasks can be performed by more than twoprocessing devices.

Processing unit 110 can include various types of devices. For example,processing unit 110 may include various devices, such as a controller,an image preprocessor, a central processing unit (CPU), supportcircuits, digital signal processors, integrated circuits, memory, or anyother types of devices for image processing and analysis. The imagepreprocessor can include a video processor for capturing, digitizing,and processing the imagery from the image sensors. The CPU can includeany number of microcontrollers or microprocessors. The support circuitscan be any number of circuits generally well known in the art, includingcache, power supply, clock, and input-output circuits. The memory canstore software that, when executed by the processor, controls theoperation of the system. The memory can include databases and imageprocessing software, including a trained system, such as a neuralnetwork, for example. The memory can include any number of random accessmemories, read only memories, flash memories, disk drives, opticalstorage, removable storage, and other types of storage. In one instance,the memory can be separate from the processing unit 110. In anotherinstance, the memory can be integrated into the processing unit 110.

Each memory 140, 150 can include software instructions that whenexecuted by a processor (e.g., application processor 180 and/or imageprocessor 190), can control operation of various aspects of system 100.These memory units can include various databases and image processingsoftware. The memory units can include random access memory, read onlymemory, flash memory, disk drives, optical storage, tape storage,removable storage, and/or any other types of storage. In some examples,memory units 140, 150 can be separate from the application processor 180and/or image processor 190. In other embodiments, these memory units canbe integrated into application processor 180 and/or image processor 190.

In some embodiments, the system can include a position sensor 130. Theposition sensor 130 can include any type of device suitable fordetermining a location associated with at least one component of system100. In some embodiments, position sensor 130 can include a GPSreceiver. Such receivers can determine a user position and velocity byprocessing signals broadcasted by global positioning system satellites.Position information from position sensor 130 can be made available toapplication processor 180 and/or image processor 190.

In some embodiments, the system 100 can be operatively connectible tovarious systems, devices and units onboard a vehicle in which the system100 can be mounted, and through any suitable interfaces (e.g., acommunication bus) the system 100 can communicate with the vehicle'ssystems. Examples of vehicle systems with which the system 100 cancooperate include: a throttling system, a braking system, and a steeringsystem.

In some embodiments, the system 100 can include a user interface 170.User interface 170 can include any device suitable for providinginformation to or for receiving inputs from one or more users of system100, including, for example, a touchscreen, microphone, keyboard,pointer devices, track wheels, cameras, knobs, buttons, etc. Informationcan be provided by the system 100, through the user interface 170, tothe user.

In some embodiments, the system 100 can include a map database 160. Themap database 160 can include any type of database for storing digitalmap data. In some examples, map database 160 can include data relatingto a position, in a reference coordinate system, of various items,including roads, water features, geographic features, points ofinterest, etc. Map database 160 can store not only the locations of suchitems, but also descriptors relating to those items, including, forexample, names associated with any of the stored features and otherinformation about them. For example, locations and types of knownobstacles can be included in the database, information about atopography of a road or a grade of certain points along a road, etc. Insome embodiments, map database 160 can be physically located with othercomponents of system 100. Alternatively or additionally, map database160 or a portion thereof can be located remotely with respect to othercomponents of system 100 (e.g., processing unit 110). In suchembodiments, information from map database 160 can be downloaded over awired or wireless data connection to a network (e.g., over a cellularnetwork and/or the Internet, etc.).

Image capture devices 122, 124, and 126 can each include any type ofdevice suitable for capturing at least one image from an environment.Moreover, any number of image capture devices can be used to acquireimages for input to the image processor. Some examples of the presentlydisclosed subject matter can include or can be implemented with only asingle-image capture device, while other examples can include or can beimplemented with two, three, or even four or more image capture devices.Image capture devices 122, 124, and 126 will be further described withreference to FIGS. 2B-2E, below.

It would be appreciated that the system 100 can include or can beoperatively associated with other types of sensors, including forexample: an acoustic sensor, a RF sensor (e.g., radar transceiver), aLIDAR sensor. Such sensors can be used independently of or incooperation with the image acquisition device 120. For example, the datafrom the radar system (not shown) can be used for validating theprocessed information that is received from processing images acquiredby the image acquisition device 120, e.g., to filter certain falsepositives resulting from processing images acquired by the imageacquisition device 120, or it can be combined with or otherwisecompliment the image data from the image acquisition device 120, or someprocessed variation or derivative of the image data from the imageacquisition device 120.

System 100, or various components thereof, can be incorporated intovarious different platforms. In some embodiments, system 100 may beincluded on a vehicle 200, as shown in FIG. 2A. For example, vehicle 200can be equipped with a processing unit 110 and any of the othercomponents of system 100, as described above relative to FIG. 1. Whilein some embodiments vehicle 200 can be equipped with only a single-imagecapture device (e.g., camera), in other embodiments, such as thosediscussed in connection with FIGS. 2B-2E, multiple image capture devicescan be used. For example, either of image capture devices 122 and 124 ofvehicle 200, as shown in FIG. 2A, can be part of an ADAS (AdvancedDriver Assistance Systems) imaging set.

The image capture devices included on vehicle 200 as part of the imageacquisition unit 120 can be positioned at any suitable location. In someembodiments, as shown in FIGS. 2A-2E and 3A-3C, image capture device 122can be located in the vicinity of the rearview mirror. This position mayprovide a line of sight similar to that of the driver of vehicle 200,which can aid in determining what is and is not visible to the driver.

Other locations for the image capture devices of image acquisition unit120 can also be used. For example, image capture device 124 can belocated on or in a bumper of vehicle 200. Such a location can beespecially suitable for image capture devices having a wide field ofview. The line of sight of bumper-located image capture devices can bedifferent from that of the driver. The image capture devices (e.g.,image capture devices 122, 124, and 126) can also be located in otherlocations. For example, the image capture devices may be located on orin one or both of the side mirrors of vehicle 200, on the roof ofvehicle 200, on the hood of vehicle 200, on the trunk of vehicle 200, onthe sides of vehicle 200, mounted on, positioned behind, or positionedin front of any of the windows of vehicle 200, and mounted in or nearlight figures on the front and/or back of vehicle 200, etc. The imagecapture unit 120, or an image capture device that is one of a pluralityof image capture devices that are used in an image capture unit 120, canhave a field-of-view (FOV) that is different than the FOV of a driver ofa vehicle, and not always see the same objects. In one example, the FOVof the image acquisition unit 120 can extend beyond the FOV of a typicaldriver and can thus image objects which are outside the FOV of thedriver. In yet another example, the FOV of the image acquisition unit120 is some portion of the FOV of the driver. In some embodiments, theFOV of the image acquisition unit 120 corresponding to a sector whichcovers an area of a road ahead of a vehicle and possibly alsosurroundings of the road.

In addition to image capture devices, vehicle 200 can be include variousother components of system 100. For example, processing unit 110 may beincluded on vehicle 200 either integrated with or separate from anengine control unit (ECU) of the vehicle. Vehicle 200 may also beequipped with a position sensor 130, such as a GPS receiver and may alsoinclude a map database 160 and memory units 140 and 150.

FIG. 2A is a diagrammatic side view representation of a vehicle imagingsystem according to examples of the presently disclosed subject matter.FIG. 2B is a diagrammatic top view illustration of the example shown inFIG. 2A. As illustrated in FIG. 2B, the disclosed examples can include avehicle 200 including in its body a system 100 with a first imagecapture device 122 positioned in the vicinity of the rearview mirrorand/or near the driver of vehicle 200, a second image capture device 124positioned on or in a bumper region (e.g., one of bumper regions 210) ofvehicle 200, and a processing unit 110.

As illustrated in FIG. 2C, image capture devices 122 and 124 may both bepositioned in the vicinity of the rearview mirror and/or near the driverof vehicle 200. Additionally, while two image capture devices 122 and124 are shown in FIGS. 2B and 2C, it should be understood that otherembodiments may include more than two image capture devices. Forexample, in the embodiment shown in FIG. 2D, first, second, and thirdimage capture devices 122, 124, and 126, are included in the system 100of vehicle 200.

As shown in FIG. 2D, image capture devices 122, 124, and 126 may bepositioned in the vicinity of the rearview mirror and/or near the driverseat of vehicle 200. The disclosed examples are not limited to anyparticular number and configuration of the image capture devices, andthe image capture devices may be positioned in any appropriate locationwithin and/or on vehicle 200.

It is also to be understood that disclosed embodiments are not limitedto a particular type of vehicle 200 and may be applicable to all typesof vehicles including automobiles, trucks, trailers, motorcycles,bicycles, self-balancing transport devices and other types of vehicles.

The first image capture device 122 can include any suitable type ofimage capture device. Image capture device 122 can include an opticalaxis. In one instance, the image capture device 122 can include anAptina M9V024 WVGA sensor with a global shutter. In another example, arolling shutter sensor can be used. Image acquisition unit 120, and anyimage capture device which is implemented as part of the imageacquisition unit 120, can have any desired image resolution. Forexample, image capture device 122 can provide a resolution of 1280×960pixels and can include a rolling shutter.

Image acquisition unit 120, and any image capture device which isimplemented as part of the image acquisition unit 120, can includevarious optical elements. In some embodiments one or more lenses can beincluded, for example, to provide a desired focal length and field ofview for the image acquisition unit 120, and for any image capturedevice which is implemented as part of the image acquisition unit 120.In some examples, an image capture device which is implemented as partof the image acquisition unit 120 can include or be associated with anyoptical elements, such as a 6 mm lens or a 12 mm lens, for example. Insome examples, image capture device 122 can be arranged to captureimages having a desired (and known) field-of-view (FOV).

The first image capture device 122 may have a scan rate associated withacquisition of each of the first series of image scan lines. The scanrate may refer to a rate at which an image sensor can acquire image dataassociated with each pixel included in a particular scan line.

FIG. 2E is a diagrammatic representation of vehicle control systems,according to examples of the presently disclosed subject matter. Asindicated in FIG. 2E, vehicle 200 can include throttling system 220,braking system 230, and steering system 240. System 100 can provideinputs (e.g., control signals) to one or more of throttling system 220,braking system 230, and steering system 240 over one or more data links(e.g., any wired and/or wireless link or links for transmitting data).For example, based on analysis of images acquired by image capturedevices 122, 124, and/or 126, system 100 can provide control signals toone or more of throttling system 220, braking system 230, and steeringsystem 240 to navigate vehicle 200 (e.g., by causing an acceleration, aturn, a lane shift, etc.). Further, system 100 can receive inputs fromone or more of throttling system 220, braking system 230, and steeringsystem 240 indicating operating conditions of vehicle 200 (e.g., speed,whether vehicle 200 is braking and/or turning, etc.).

As shown in FIG. 3, vehicle 200 may also include a user interface 170for interacting with a driver or a passenger of vehicle 200. Forexample, user interface 170 in a vehicle application may include a touchscreen 320, knobs 330, buttons 340, and a microphone 350. A driver orpassenger of vehicle 200 may also use handles (e.g., located on or nearthe steering column of vehicle 200 including, for example, turn signalhandles), buttons (e.g., located on the steering wheel of vehicle 200),and the like, to interact with system 100. In some embodiments,microphone 350 may be positioned adjacent to a rearview mirror 310.Similarly, in some embodiments, image capture device 122 may be locatednear rearview mirror 310. In some embodiments, user interface 170 mayalso include one or more speakers 360 (e.g., speakers of a vehicle audiosystem). For example, system 100 may provide various notifications(e.g., alerts) via speakers 360.

As will be appreciated by a person skilled in the art having the benefitof this disclosure, numerous variations and/or modifications may be madeto the foregoing disclosed embodiments. For example, not all componentsare essential for the operation of system 100. Further, any componentmay be located in any appropriate part of system 100 and the componentsmay be rearranged into a variety of configurations while providing thefunctionality of the disclosed embodiments. Therefore, the foregoingconfigurations are examples and, regardless of the configurationsdiscussed above, system 100 can provide a wide range of functionality toanalyze the surroundings of vehicle 200 and, in response to thisanalysis, navigate and/or otherwise control and/or operate vehicle 200.Navigation, control, and/or operation of vehicle 200 may includeenabling and/or disabling (directly or via intermediary controllers,such as the controllers mentioned above) various features, components,devices, modes, systems, and/or subsystems associated with vehicle 200.Navigation, control, and/or operation may alternately or additionallyinclude interaction with a user, driver, passenger, passerby, and/orother vehicle or user, which may be located inside or outside vehicle200, for example by providing visual, audio, haptic, and/or othersensory alerts and/or indications.

As discussed below in further detail and consistent with variousdisclosed embodiments, system 100 may provide a variety of featuresrelated to autonomous driving, semi-autonomous driving and/or driverassist technology. For example, system 100 may analyze image data,position data (e.g., GPS location information), map data, speed data,and/or data from sensors included in vehicle 200. System 100 may collectthe data for analysis from, for example, image acquisition unit 120,position sensor 130, and other sensors. Further, system 100 may analyzethe collected data to determine whether or not vehicle 200 should take acertain action, and then automatically take the determined actionwithout human intervention. It would be appreciated that in some cases,the actions taken automatically by the vehicle are under humansupervision, and the ability of the human to intervene adjust abort oroverride the machine action is enabled under certain circumstances or atall times. For example, when vehicle 200 navigates without humanintervention, system 100 may automatically control the braking,acceleration, and/or steering of vehicle 200 (e.g., by sending controlsignals to one or more of throttling system 220, braking system 230, andsteering system 240). Further, system 100 may analyze the collected dataand issue warnings, indications, recommendations, alerts, orinstructions to a driver, passenger, user, or other person inside oroutside of the vehicle (or to other vehicles) based on the analysis ofthe collected data. Additional details regarding the various embodimentsthat are provided by system 100 are provided below.

The system may apply error correction coding in a highly efficientmanner in terms of throughput and low latency. The arrangement of datasub-blocks and error correction code sub-blocks at the same row, thewriting of data sub-blocks and error correction sub-blocks to a row of adynamic memory module while the row is open may increase the writethroughput by a factor of two and the caching of the error correctionblocks in a cache memory may also increase the reading throughput by afactor of two.

This increase in reading and writing throughput dramatically reduces thepenalty associated with error correction—and enables to apply errorcorrection coding (ECC) even to (but not necessarily to) all the regionsin the dynamic memory module, for example (but not limited to) sensorimages—and not only code.

Applying ECC on sensor images and especially lower resolution imagessuch as radar sensor acquired images and LIDAR sensor acquired imagesincreases the reliability of such images, reduces required level ofredundancy and so allows using fewer number of sensors—thereby reducingthe cost of the system, simplifying the system and reducing the size,and energy consumption of the system. Accordingly—applying the ECC onLIDAR images may replace the need of using redundant LIDAR sensors tocompensate for LIDAR image errors.

The low penalty associated with applying the ECC may ease the applyingof ECC on the images acquired by the image acquisition unit 120 and alsoon any processed image (or temporary data) generated during any one outof autonomous driving operations, semi-autonomous driving operationsand/or driver assist technology operations such as but not limited toautomatic lane tracking, pedestrian detection, autonomous breaking, andthe like.

Applying ECC on code and on data of various types increases thereliability of the outputs of the system and allows to operate thevehicle in a more optimal manner—even with lower safeguards.

Applying ECC on code and on data of various types reduces the chances offailures, reduces the system Failure In Time (FIT) parameter—andprovides a more robust system.

FIGS. 4 and 5 illustrates an example of a dynamic memory module 410 anda dynamic memory controller 420. The dynamic memory module may be a DRAMand/or a DDR (double data rate) memory module. In some of the examplesbelow it is assumed that the dynamic memory module is a DDR memorymodule.

An in-line ECC configuration may be used—in which the error correctionsub-blocks (also referred to as ECC sub-blocks) and data sub-blocks aresent (from the dynamic memory module and to the dynamic memory module)over the same communication link—in a serial manner Thus, ECC bits anddata bits are sent over the same pins (or other interface) of thedynamic memory module—in a serial manner. The in-line ECC configurationmay require only a single dynamic memory module for storing the ECC anddata and is LPDDR4 compliant.

The dynamic memory module may be, for example, any one of memory modules140 and 150 of FIG. 1.

The dynamic memory module 410 may receive (over communication link 411)data sub-blocks that originated from data generators such as applicationprocessor 180 and image processor 190 of FIG. 1 (or from any other datagenerator).

The dynamic memory module 410 may output (over communication link 411)data sub-blocks to data consumers such as application processor 180 andimage processor 190 of FIG. 1 (or to any other data consumer).

In FIG. 4 the dynamic memory controller is coupled to an ECC unit 430.In FIG. 5 the ECC unit 430 is included in the dynamic memory controller420.

The dynamic memory module 410 may include one or more memory banks.

FIG. 4 illustrates a single memory bank 418 while FIG. 5 illustrateseight memory banks 411-418. The dynamic memory module 410 may includeany number of memory banks. For DDR use performance reasons, it'sbeneficial to store the ECC blocks together with the corresponding datablocks in the same DDR row.

During write operations the ECC unit 430 may apply ECC operations onincoming data sub-blocks to provide ECC sub-blocks.

Every data write to DDR requires the corresponding ECC generation andsubsequent ECC write to ECC cache/buffer (432).

Any ECC that is buffered in DDR controller for write data, should bewritten to memory at some point.

There may be various possible triggers for writing the ECC to DDR. Forexample:

-   -   There is a need to buffer other data commands and LRU ECC may        need to be replaced    -   There is a need to clean the DDR controller state before        entering into low power modes

During read operations the ECC unit 430 may apply ECC check on datasub-blocks read from the dynamic memory module 410 in order to detecterrors and correct errors. Every data read from DDR requires asubsequent corresponding ECC read, unless this particular ECC is alreadypresent in ECC cache/buffer

The ECC unit 430 may perform ECC operations (generation or check) on allthe data stored in the dynamic memory module 410 or on predefinedregions of the dynamic memory module 410 that require ECC protection.

FIG. 5 illustrates a row 418(2) of memory bank 418 of dynamic memorymodule 410 that stores seven data blocks 401-407 and an ECC block 408.Memory bank 418 may have any number of rows—and rows 418(1), 418(2) and418(80) are only examples of some of the rows of memory bank 418.

Each data block may include multiple data sub-blocks—for example datasub-blocks 410(1)-401(8) of data block 401. The data sub-blocks may betransferred during one or more data bursts.

ECC block 408 may include ECC sub-blocks—for example ECC sub-blocks408(1,1)-408(1,8) that are related to data sub-blocks 401(1)-401(8).

The data blocks and the ECC block may be 512-byte long and eachsub-block may be 64-byte long. Other sizes may be supported. Therelationship between the size and/or number of the ECC block and thesize and/or number of data blocks per row may differ from thoseillustrated in FIG. 5.

An ECC sub-block may be calculated by the ECC unit 430 whenever a datasub-block is received or in a later point of time.

An ECC sub-block may be cached in an ECC cache 432 before the ECCsub-block is written to the dynamic memory module 410. The ECC sub-blockmay be written to the dynamic memory module 410 at any time after theECC sub-block is calculated. ECC cache 432 is just an example or amemory unit that may store the ECC sub-block. For example—a buffer maybe used for storing the ECC sub-block.

Dynamic memory module 410 may include one or more memory banks. In eachmemory bank, up to a single row may be opened (activated) at a time.

A write operation to a certain row (that is currently closed) of thedynamic memory module 410 requires to close another row (that iscurrently open), activate the certain row and write one or more datasub-blocks to the certain row.

It has been found that it is highly beneficial to write to the certainrow all ECC sub-blocks that (a) are related to data sub-blocks stored inthat certain row and (b) were generated while the certain row is stillopen—before the certain row is closed.

Writing the ECC sub-blocks related to the certain row—after the certainrow is closed—required to close a currently active row, activate (again)the certain row and write one or more ECC sub-blocks to the certain row.This process is time and DDR bandwidth consuming.

For example—Writing the ECC sub-blocks related to the certain row—afterthe certain row is closed—Every 7 bursts of data, the current row shouldbe PRECHARGED and another ECC row activated and written. The latenciesare:

7*(tRP+tRCD+WL+8_(data)*4+tRP+tRCD+WL+I _(ECC)*4)=1092 cycles

Wherein tRP—Row precharge time; tRCD—RAS-to-CAS delay (RAS—rowactivation strobe, CAS—column activation strobe) and WL—write latency.And wherein it is assumed that tRP=tRCD=RL=WL=20 cycles and burstlength=16 (64 bytes, 4 cycles).

For example—Writing the ECC sub-blocks related to the certain row—beforethe certain row is closed—Every 7 bursts of data, the additional 1 burstof ECC should be written to same row. ECC does not require additionalPRECHARGE/ACTIVATE command and can be written back to back with thedata. The latencies are: tRP+tRCD+WL+7*(8_(data)+1_(ECC))*4=312 cycles.Yet for another example of parameters that may be used Activation:tRP=tRCD=RL=WL=20 cycles and burst length=16 (64 bytes, 4 cycles).

The dynamic memory controller 420 controls the various operationsrelated to the dynamic memory module 410 (including the write operation,the pre-charging operation and the activating operation) and maydetermine when to perform the writing of the one or more ECC sub-blocksbefore the certain row is closed.

The dynamic memory controller 420 may receive access requests (denoted442 in FIG. 5) and convert these access requests to dynamic memorycontroller commands such as pre-charging row, activate row and read orwrite row (see box 443 in FIG. 5).

FIG. 5 illustrates two triplets of dynamic memory controller commands:

1. Pre-charge row 418(1).

2. Activate row 418(2).

3. Write data to row 418(2).

4. Pre-charge row 418(2)

5. Activate another row.

6. Read or write to the other row.

It should be noted that after activating the row multiple read and/orwrite commands may be executed.

It is beneficial to write to row 418(2) all the ECC sub-blockscalculated during the execution of the third command (read or write row418(2)) before the execution of the fourth command (pre-charge row418(2)).

Thus—the dynamic memory controller commands may include:

1. Pre-charge row 418(1).

2. Activate row 418(2).

3. Write data to row 418(2).

-   -   i. Write ECC to row 418(2).

4. Pre-charge row 418(2)

5. Activate another row.

6. Read or write to the other row.

FIG. 6 illustrates two timing diagrams 600 and 602.

Timing diagram 600 illustrates the following sequence of events (Tdenotes a point in time):

1. T1 611—activate certain row 601.

2. T2 612—receive a data sub-block 602.

3. T3 613—calculate ECC sub-block related to the data sub-block 603.

4. T4 614—write data sub-block to the dynamic memory module 604.

5. T15 625—write ECC sub-block to the dynamic memory module 605.

6. T16 626—pre-charge the certain row 606.

It is noted that event 603 may follow event 604, that events 603 and 604may occur simultaneously.

It should be noted that the writing of the data sub-blocks to thedynamic memory module may be executed upon a reception of a single datasub-block, that multiple data sub-blocks may be aggregated before theyare written to the dynamic memory module, and the like.

Timing diagram 602 illustrates two repetitions of events 602, 603 and604 before the occurrence of event 605.

Timing diagram 600 illustrates the following sequence of events (Tdenotes a point in time):

1. T1 611—activate certain row 601.

2. T2 612—receive a data sub-block 602.

3. T3 613—calculate ECC sub-block related to the data sub-block 603.

4. T4 614—write data sub-block to the dynamic memory module 604.

5. T5 615—receive a data sub-block 602.

6. T6 616—calculate ECC sub-block related to the data sub-block 603.

7. T7 617—write data sub-block to the dynamic memory module 604.

8. T15 625—write ECC sub-block to the dynamic memory module 605.

9. T16 626—pre-charge the certain row 606.

FIG. 7 is a flow chart that illustrates method 700.

Method 700 may start by step 702 of activating a certain row of adynamic memory module.

Step 702 may be triggered by a write command that is received by adynamic memory controller.

Step 702 may be followed by step 704 of receiving (by a dynamic memorycontroller) a data sub-block to be written to the certain row of thedynamic memory module.

A data sub-block to be written to (or targeted to) the certain row maybe associated (by the dynamic memory controller or by another entity)with address information that indicates that the data-sub-block shouldbe written to the certain row.

Step 704 may be followed by steps 706 and 708.

Step 706 may include calculating an ECC sub-block related to(protecting) the data sub-block.

Step 708 may include writing the data sub-block to the dynamic memorymodule over the communication link.

Steps 706 and 708 may be followed by step 720 of writing one or more ECCsub-blocks to the certain row before the certain row is pre-charged.

The writing of the data unit to the dynamic memory module includessending the data unit over the communication link.

Method 700 utilizes the in-line ECC configuration—the same communicationline is used for conveying data bits and ECC bits—at different points oftime.

Steps 702-720 may be repeated for multiple rows—especially one row afterthe other. Each iteration a row is selected and after steps 702-720 areexecuted the method may be executed in relation to a new selected row.The certain row of FIG. 7 is an example of a selected row.

Method 700 may, for example, be executed as a part of a ADAS operationand/or an autonomous vehicle operation. Method 700 may be used for anyother purpose.

FIG. 8 illustrates a method 700 that further includes step 707 ofstoring the ECC sub-block related to the data sub-block in a cachememory (for example ECC cache 432 of FIG. 5). Step 707 follows step 706and precedes step 708.

Multiple iterations of steps 704, 706 and 708 may occur between theexecution of steps 702 and 720.

Any reference to a system should be applied, mutatis mutandis to amethod that is executed by a system and/or to a computer program productthat stores instructions that once executed by the system will cause thesystem to execute the method. The computer program product isnon-transitory and may be, for example, an integrated circuit, amagnetic memory, an optical memory, a disk, and the like.

Any reference to method should be applied, mutatis mutandis to a systemthat is configured to execute the method and/or to a computer programproduct that stores instructions that once executed by the system willcause the system to execute the method.

Any reference to a computer program product should be applied, mutatismutandis to a method that is executed by a system and/or a system thatis configured to execute the instructions stored in the computer programproduct.

The term “and/or” is additionally or alternatively.

In the foregoing specification, the invention has been described withreference to specific examples of embodiments of the invention. It will,however, be evident that various modifications and changes may be madetherein without departing from the broader spirit and scope of theinvention as set forth in the appended claims.

Moreover, the terms “front,” “back,” “top,” “bottom,” “over,” “under”and the like in the description and in the claims, if any, are used fordescriptive purposes and not necessarily for describing permanentrelative positions. It is understood that the terms so used areinterchangeable under appropriate circumstances such that theembodiments of the invention described herein are, for example, capableof operation in other orientations than those illustrated or otherwisedescribed herein.

Any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality may be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected,” or“operably coupled,” to each other to achieve the desired functionality.

Furthermore, those skilled in the art will recognize that boundariesbetween the above described operations merely illustrative. The multipleoperations may be combined into a single operation, a single operationmay be distributed in additional operations and operations may beexecuted at least partially overlapping in time. Moreover, alternativeembodiments may include multiple instances of a particular operation,and the order of operations may be altered in various other embodiments.

However, other modifications, variations and alternatives are alsopossible. The specifications and drawings are, accordingly, to beregarded in an illustrative rather than in a restrictive sense.

The phrase “may be X” indicates that condition X may be fulfilled. Thisphrase also suggests that condition X may not be fulfilled. Forexample—any reference to a system as including a certain componentshould also cover the scenario in which the system does not include thecertain component.

The terms “including”, “comprising”, “having”, “consisting” and“consisting essentially of” are used in an interchangeable manner. Forexample—any method may include at least the steps included in thefigures and/or in the specification, only the steps included in thefigures and/or the specification. The same applies to the system and themobile computer.

It will be appreciated that for simplicity and clarity of illustration,elements shown in the figures have not necessarily been drawn to scale.For example, the dimensions of some of the elements may be exaggeratedrelative to other elements for clarity. Further, where consideredappropriate, reference numerals may be repeated among the figures toindicate corresponding or analogous elements.

Also for example, in one embodiment, the illustrated examples may beimplemented as circuitry located on a single integrated circuit orwithin a same device. Alternatively, the examples may be implemented asany number of separate integrated circuits or separate devicesinterconnected with each other in a suitable manner.

Also for example, the examples, or portions thereof, may implemented assoft or code representations of physical circuitry or of logicalrepresentations convertible into physical circuitry, such as in ahardware description language of any appropriate type.

Also, the invention is not limited to physical devices or unitsimplemented in non-programmable hardware but can also be applied inprogrammable devices or units able to perform the desired devicefunctions by operating in accordance with suitable program code, such asmainframes, minicomputers, servers, workstations, personal computers,notepads, personal digital assistants, electronic games, automotive andother embedded systems, cell phones and various other wireless devices,commonly denoted in this application as ‘computer systems’.

However, other modifications, variations and alternatives are alsopossible. The specifications and drawings are, accordingly, to beregarded in an illustrative rather than in a restrictive sense.

In the claims, any reference signs placed between parentheses shall notbe construed as limiting the claim. The word ‘comprising’ does notexclude the presence of other elements or steps then those listed in aclaim. Furthermore, the terms “a” or “an,” as used herein, are definedas one as or more than one. Also, the use of introductory phrases suchas “at least one” and “one or more” in the claims should not beconstrued to imply that the introduction of another claim element by theindefinite articles “a” or “an” limits any particular claim containingsuch introduced claim element to inventions containing only one suchelement, even when the same claim includes the introductory phrases “oneor more” or “at least one” and indefinite articles such as “a” or “an.”The same holds true for the use of definite articles. Unless statedotherwise, terms such as “first” and “second” are used to arbitrarilydistinguish between the elements such terms describe. Thus, these termsare not necessarily intended to indicate temporal or otherprioritization of such elements the mere fact that certain measures arerecited in mutually different claims does not indicate that acombination of these measures cannot be used to advantage.

While certain features of the invention have been illustrated anddescribed herein, many modifications, substitutions, changes, andequivalents will now occur to those of ordinary skill in the art. It is,therefore, to be understood that the appended claims are intended tocover all such modifications and changes as fall within the true spiritof the invention.

Any combination of any component of any component and/or unit of systemthat is illustrated in any of the figures and/or specification and/orthe claims may be provided.

Any combination of any system illustrated in any of the figures and/orspecification and/or the claims may be provided.

Any combination of steps, operations and/or methods illustrated in anyof the figures and/or specification and/or the claims may be provided.

Any combination of operations illustrated in any of the figures and/orspecification and/or the claims may be provided.

Any combination of methods illustrated in any of the figures and/orspecification and/or the claims may be provided.

Moreover, while illustrative embodiments have been described herein, thescope of any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations and/or alterations as would be appreciated bythose skilled in the art based on the present disclosure. Thelimitations in the claims are to be interpreted broadly based on thelanguage employed in the claims and not limited to examples described inthe present specification or during the prosecution of the application.The examples are to be construed as non-exclusive. Furthermore, thesteps of the disclosed methods may be modified in any manner, includingby reordering steps and/or inserting or deleting steps. It is intended,therefore, that the specification and examples be considered asillustrative only, with a true scope and spirit being indicated by thefollowing claims and their full scope of equivalents.

What is claimed is:
 1. A method for error correction, the methodcomprises: opening a selected row of a memory bank out of multiplememory banks of a dynamic memory module; receiving selected datasub-blocks, while the selected row is open, by the dynamic memorymodule, wherein the selected data sub-blocks are received over acommunication link and are targeted to be written to the selected row;calculating, while the selected row is open and by an error correctionunit, selected error correction code sub-blocks that are related to theselected data sub-blocks; caching the selected error correction codesub-blocks in a cache memory that differs from the dynamic memorymodule; writing, to the selected row, the selected error correction codesub-blocks while the selected row is open; wherein the writing comprisessending the selected error correction code sub-blocks to the dynamicmemory module over the communication link; and closing the selected row.2. The method according to claim 2 wherein the closing of the selectedrow comprises pre-charging the selected row.
 3. The method according toclaim 1 comprising storing in the selected row more data sub-blocks thanerror correction code sub-blocks.
 4. The method according to claim 1comprising storing, in the selected row, data blocks and a single errorcorrection code block; wherein each data block comprises datasub-blocks, and wherein the single error correction code block compriseserror correction code sub-blocks.
 5. The method according to claim 1comprising: opening a new selected row that belongs to any of themultiple memory banks; receiving by the dynamic memory module, over thecommunication link and while the new selected row is open, new selecteddata sub-blocks that are targeted to be written to the new selected row;calculating, by the error correction unit, while the new selected row isopen, new selected error correction code sub-blocks that are related tothe new selected data sub-blocks; caching the new selected errorcorrection code sub-blocks in the cache memory; writing, to the newselected row, the new selected error correction code sub-blocks whilethe new selected row is open; wherein the writing comprises sending thenew selected error correction code sub-blocks to the dynamic memorymodule over the communication link; and closing the new selected row. 6.The method according to claim 1 comprising: receiving a request forreading a first plurality of data sub-blocks blocks that are stored atdifferent memory banks of the multiple memory banks of the dynamicmemory module; checking whether the cache memory stores error correctionsub-blocks that are related to any of the first plurality of datasub-blocks; retrieving, from the dynamic memory module and over thecommunication link, the first plurality of data sub-blocks blocks;retrieving error correction sub-blocks that are related to the firstplurality of data sub-blocks; wherein the retrieving comprisesretrieving from the cache memory, instead from the dynamic memorymodule, any error correction sub-block that is stored in the cachememory and is related to any of the first plurality of data sub-blocks;and error correcting the the first plurality of data sub-blocks toprovide a first plurality of error corrected data sub-blocks, using theerror correction sub-blocks that are related to the first plurality ofdata sub-blocks.
 7. The method according to claim 6 comprisingprocessing the first plurality of error corrected data sub-blocks duringat least one operation out of an autonomous driving operation, asemi-autonomous driving operation and a driver assist technologyoperation.
 8. The method according to claim 6 comprising initiating ahuman takeover of control of a vehicle, wherein the control is handedfrom an autonomous control module of the vehicle.
 9. The methodaccording to claim 1, wherein the data sub-blocks comprise segments ofone or more images acquired by a radar.
 10. The method according toclaim 1, wherein the data sub-blocks comprise segments of one or moreimages acquired by a LIDAR sensor.
 11. The method according to claim 1,wherein the data sub-blocks comprise segments of one or more cameraimages.
 12. The method according to claim 1, wherein the data sub-blockscomprise executable code.
 13. A system having error correctioncapabilities, the system comprises a dynamic memory controller, adynamic memory module that is coupled to a communication link; a cachememory, and an error correction code unit; wherein the dynamic memorycontroller is arranged to (a) open a selected row of a memory bank outof multiple memory banks of a dynamic memory module; (b) receive, whilethe selected row is open, selected data sub-blocks that are targeted tobe written to the selected row; wherein the dynamic memory module isconfigured to receive the selected data sub-blocks from the dynamicmemory controller and over a communication link; wherein the errorcorrection unit is arranged to calculate, while the selected row isopen, selected error correction code sub-blocks that are related to theselected data sub-blocks; wherein the cache memory differs from thedynamic memory module and is arranged to cache the selected errorcorrection code sub-blocks; wherein the dynamic memory controller isalso arranged to (a) send the selected error correction code sub-blocksto the dynamic memory module over the communication link; (b) write, tothe selected row and over the communication link, the selected errorcorrection code sub-blocks while the selected row is open; and (c) closethe selected row.
 14. The system according to claim 13 wherein thedynamic memory controller comprises the error correction code unit andthe cache memory.
 15. The system according to claim 13 wherein thedynamic memory controller does not include the error correction codeunit and the cache memory.
 16. The system according to claim 13 whereinthe dynamic memory controller is arranged to close the selected row bypre-charging the selected row.
 17. The system according to claim 13wherein the dynamic memory module is arranged to store in the selectedrow more data sub-blocks that error correction code sub-blocks.
 18. Thesystem according to claim 13 wherein the dynamic memory module isarranged to store, in the selected row, data blocks and a single errorcorrection code block; wherein each data block comprises datasub-blocks, and wherein the single error correction code block compriseserror correction code sub-blocks.
 19. The system according to claim 13wherein the dynamic memory controller is arranged to (a) open a newselected row of any memory bank of the multiple memory; (b) receive,while the new selected row is open, new selected data sub-blocks thatare targeted to be written to the selected row; (c) send the newselected data sub-blocks to the dynamic memory module over thecommunication link; wherein the error correction unit is arranged tocalculate, while the new selected row is open, new selected errorcorrection code sub-blocks that are related to the new selected datasub-blocks; and wherein the dynamic memory controller is also arrangedto (a) write, to the new selected row over the communication link, thenew selected error correction code sub-blocks while the new selected rowis open; and (b) close the new selected row.
 20. The system according toclaim 13 wherein the dynamic memory controller is arranged to (a)receive a request for reading a first plurality of data sub-blocksblocks that are stored at different memory bank of the multiple memorybanks of the dynamic memory module; (b) check whether the cache memorystores error correction sub-blocks that are related to any of the firstplurality of data sub-blocks; (c) retrieve from the dynamic memorymodule the first plurality of data sub-blocks blocks; (d) retrieve errorcorrection sub-blocks that are related to the first plurality of datasub-blocks; wherein the retrieve of the error correction sub-blockscomprises retrieving from the cache memory, instead from the dynamicmemory module, any error correction sub-block that is stored in thecache memory and is related to any of the first plurality of datasub-blocks; and wherein the error correction unit is arranged to errorcorrect the first plurality of data sub-blocks to provide a firstplurality of error corrected data sub-blocks, using the error correctionsub-blocks that are related to the first plurality of data sub-blocks.21. The system according to claim 20 wherein the processing unit isarranged to process the first plurality of error corrected datasub-blocks during at least one operation out of an autonomous drivingoperation, a semi-autonomous driving operation and a driver assisttechnology.
 22. The system according to claim 20 wherein the processingunit is arranged to initiate a human takeover of control of a vehicle,wherein the control is handed from an autonomous control module of thevehicle.
 23. The system according to claim 13, wherein the datasub-blocks comprise segments of one or more images acquired by a radar.24. The system according to claim 13, wherein the data sub-blockscomprise segments of one or more images acquired by the LIDAR sensor.25. The system according to claim 13, wherein the data sub-blockscomprise segments of one or more camera images.
 26. The system accordingto claim 13, wherein the data sub-blocks comprise executable code.
 27. Acomputer program product that stores instructions that once executed bya computerized system may cause the computerized system to execute thesteps of: opening a selected row of a memory bank out of multiple memorybanks of a dynamic memory module; receiving selected data sub-blocks,while the selected row is open, by the dynamic memory module; whereinthe selected data sub-blocks are received over a communication link andare targeted to be written to the selected row; calculating, while theselected row is open and by an error correction unit, selected errorcorrection code sub-blocks that are related to the selected datasub-blocks; caching the selected error correction code sub-blocks in acache memory that differs from the dynamic memory module; writing, tothe selected row, the selected error correction code sub-blocks whilethe selected row is open; wherein the writing comprises sending theselected error correction code sub-blocks to the dynamic memory moduleover the communication link; and closing the selected row.
 28. Thecomputer program product according to claim 28 wherein the closing ofthe selected row comprises pre-charging the selected row.
 29. Thecomputer program product according to claim 27 that stores instructionsfor storing in the selected row more data sub-blocks that errorcorrection code sub-blocks.
 30. The computer program product accordingto claim 27 that stores instructions for storing, in the selected row,data blocks and a single error correction code block; wherein each datablock comprises data sub-blocks, and wherein the single error correctioncode block comprises error correction code sub-blocks.
 31. The computerprogram product according to claim 27 that stores instructions for:opening a new selected row that belongs to any of the multiple memorybanks; receiving by the dynamic memory module, over the communicationlink and while the new selected row is open, new selected datasub-blocks that are targeted to be written to the new selected row;calculating, by the error correction unit, while the new selected row isopen, new selected error correction code sub-blocks that are related tothe new selected data sub-blocks; caching the new selected errorcorrection code sub-blocks in the cache memory; writing, to the newselected row, the new selected error correction code sub-blocks whilethe new selected row is open; wherein the writing comprises sending thenew selected error correction code sub-blocks to the dynamic memorymodule over the communication link; and closing the new selected row.32. The computer program product according to claim 27 that storesinstructions for: receiving a request for reading a first plurality ofdata sub-blocks blocks that are stored at different memory bank of themultiple memory banks of the dynamic memory module; checking whether thecache memory stores error correction sub-blocks that are related to anyof the first plurality of data sub-blocks; retrieving from the dynamicmemory module the first plurality of data sub-blocks blocks; retrievingerror correction sub-blocks that are related to the first plurality ofdata sub-blocks; wherein the retrieving comprises retrieving from thecache memory, instead from the dynamic memory module, any errorcorrection sub-block that is stored in the cache memory and is relatedto any of the first plurality of data sub-blocks; and error correctingthe first plurality of data sub-blocks to provide a first plurality oferror corrected data sub-blocks, using the error correction sub-blocksthat are related to the first plurality of data sub-blocks.
 33. Thecomputer program product according to claim 32 that stores instructionsfor processing the first plurality of error corrected data sub-blocksduring at least one operation out of an autonomous driving operation, asemi-autonomous driving operation and a driver assist technologyoperation.
 34. The computer program product according to claim 32 thatstores instructions for initiating a human takeover of control of avehicle, wherein the control is handed from an autonomous control moduleof the vehicle.
 35. The computer program product according to claim 27wherein the data sub-blocks comprise segments of one or more imagesacquired by a radar.
 36. The computer program product according to claim27 wherein the data sub-blocks comprise segments of one or more imagesacquired by a LIDAR sensor.
 37. The computer program product accordingto claim 27 wherein the data sub-blocks comprise segments of one or morecamera images.
 38. The computer program product according to claim 17wherein the data sub-blocks comprise executable code.